Size Change: +16 B (0%)

Total Size: 1.62 MB

_{compressed-size-action}

Love the work done in this PR to preserve the signature of the debounced function!

One question I have is that this basically replicates the "we don't care about these arguments" approach from before but it makes the documentation pretty bad. So the alternative is to explicitly document each of the parameters to debounce. It's highly unlikely that the parameters to debounce are going to change so I think it's safe to do so. What do y'all think? I think it would be a big improvement over what we have now.

I also believe that our docs should be more detailed. We now have two choices:

• document each parameter explicitly. This would greatly help a developer getting started with useDebounce, but would mean that we'd be in charge of updating these docs when Lodash's debounce function updates
• Explicitly link to the debounce docs. This would mean that our docs wouldn't be exhaustive, but also that we wouldn't need to worry about keeping the docs in sync with lodash (apart from potentially linking to the correct version number)

document each parameter explicitly. This would greatly help a developer getting started with useDebounce, but would mean that we'd be in charge of updating these docs when Lodash's debounce function updates

I strongly prefer this option as it also improves the inline auto-complete based documentation, not just the README docs. I'll go ahead and make this change.